home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
windows
/
wregnode.zip
/
READTHIS.FIL
< prev
next >
Wrap
Text File
|
1992-05-21
|
7KB
|
144 lines
RegNode v.1.00
(C)1982, Ray L. Kaliss
Instructions for use with Win*Net,
the Windows file distribution network!
---------------------------------------------------------------------
Hello and welcome to Win*Net, if you're new, and thanks a million, if
you're a grizzled veteran of the file-distribution wars. This document
supplements the instructions for the use of RegNode included in the
RegNode archive with specific hints/instuctions for Win*Net participating
nodes. This document was printed on recycled paper, if that's what was
in your printer. The accompanying software comes with no guarantees
whatsoever. Contents may settle during shipment, and your mileage may
vary.
------ What's this "REGNODE" thing anyway? -----
Regnode is a specialized database compiler for use with FidoNet-
compatible systems, and is used to collect and compile the "WINNET.MAP"
file listing of nodes hooked into the Win*Net distribution system.
This is useful within Win*Net for determining routing and "member"
nodes, and the comipled listing (as periodically updated) will be
distributed upblicly so that (1) users know what BBS'es carry Win*Net;
and (2) prospective new BBS'es know places to look for a possible
link into the system. Win*Net has grown to the point that it is
impossible to keep such a list manually. RegNode will simplify and
automate the list-making process. At least, that's the intent.
There is far more complete, generalized documentation in the archive,
in the file REGNODE.PRN. You should read that document for instructions
on RegNode setup and operation. You should read this document for
information specific to using RegNode with the Win*Net system. You
should read Tristram Shandy by Lawrence Sterne for an understanding
of the use of the persona in early English novel forms.
---- How's it work? ----
RegNode works on a bottom-up distribution system. As Win*Net files are
sent "down" through a branching distribution system, RegNode "registration"
files are sent "upstream" from end nodes to their uplinks, and so on
in turn until all the information arrives here at 1:130/38 and is compiled
and published as the file WINNET.MAP. If you want to be listed, you *must*
assemble a registration file in the format:
@WIN
1:123/456 Joe Sysop, Another BBS, Anytown, Ohio USA 310-555-1212
Specializing in batch file menus for DOS systems.
1:123/222
...that's it. Four lines. IF YOU DON'T SEND Win*Net FILES YOU RECEIVE
ON TO ANOTHER NODE (i.e. if you are an "end node" in the Win*Net
distribution chain), just create this file, name it with the letter "W"
followed by your net/node address (no slashes), and file-attach it to
whoever feeds you the Win*Net files. You don't have to run RegNode. For
you end nodes, more information about the format of the "registration"
file is contained in REGNODE.CFG in this archive, but since you don't
need to run RegNode, you won't need a configuration file or a .LST fle
or any of that stuff. Stop reading now, create the file with any
ASCII editor, and send it to your uplink. You're done.
************* HOWEVER! **************
...if you receive Win*Net files and in turn send them with TICK or FLEA
off to other boards, you are an intermediate link rather than an end node,
and you need to run RegNode. You also need to create two files, REGNODE.CFG
and REGNODE.LST. Sample files with comments are included, and also
described in REGNODE.PRN. REGNODE.CFG contains some file-path information
for RegNode, as well as your own BBS information in the same format as
above. REGNODE.LST is a routing file, and shows the "downlinks" (nodes you
feed) who will be sending you registration files. RegNode needs both of
these to run.
When you have created these files, you are ready to run RegNode. Place the
files and the executables in one directory, change to that directory and
test your setup by entering:
REGNODE -t
...that will test your configuration. If everything looks right, force
RegNode to compile an "outfile" like this:
REGNODE -c
...you will get a file named whatever you called your "outfile" in
REGNODE.CFG. You may also get a file called REGNODE.RPT; this is a
list of the downstream nodes you named in REGNODE.LST for which
RegNode could not find a registration file. The outfile gets sent
"upstream" by file-attach. The nodes in REGNODE.RPT should perhaps
receive some friendly netmail to the effect that you haven't received
their registration file (hint, hint).
If you are a "member" of multiple file-distribution systems like SDS,
SDN, etc., you will need a separate REGNODE.CFG file for each, with a
unique name for each file. Let's say the Win*Net configuration file
is called WINNET.CFG. You can tell regnode to use this file on the
command line:
REGNODE -c WINNET
...the .CFG extension will be assumed by RegNode.
RegNode will create a couple of other files in its directory, as
indicated in the REGNODE.PRN file. These take care of themselves.
You can just leave them alone.
----- When should I run RegNode? -----
Regularly. Every now and then. Weekly, if that's how often you poll
your uplink. Every time you get a new registration file from a downlink.
During the Vernal Equinox.
I'm not going to attempt a day-of-the-month prescription for Win*Net,
because we're not as organized as some of the big guys, with named
distribution levels. Heck, we're lucky this works at all! But for the
list of nodes to be meaningful, RegNode should be run by intermediate
nodes:
(1) once, initially, when most or all of the downstream link
information is ready;
(2) on some regular basis, perhaps corresponding to a periodic
maintenance event on your BBS;
(3) any time you get a new link downstream or a new registration
file from an existing link; and
(4) in any event, at least monthly.
You can do (1) and (3) manually. You can add (2) to your batch file,
automating both the RegNode compilation and the file-attach with a
file-attach utility like PLEASE. And you can periodically test for
incoming registration files in a batch file...if, for example, all your
downlink were in nets 130 and 114, you could do something like this:
IF EXIST C:\FILE\NET\W130*.* GOTO WREGNODE
IF EXIST C:\FILE\NET\W114*.* GOTO WREGNODE
------
:WREGNODE
REGNODE -c <config filename if necessary>
PLEASE SEND <outfile name> TO <uplink>
GOTO ELSEWHERE
---- Thanks and Appreciation ----
...to Ray Kaliss of SDN for writing RegNode, and to you for helping us
keep track of Win*Net nodes!
-Larry